I'm developing a visionOS app and was able to upload new builds without any problems to the App Store. A couple pf days ago I wanted to ship another update, but now I can't submit it to the App Store anymore, because the validation failed, something related to the App Icon seems to be the issue, the logs mention CFBundleIcons.CFBundlePrimaryIcon. I have setup the App Icons here: The validation error I first got was this, mentioning a plist entry (that has not been necessary in the past) is missing. I've then added that plist entry, as described in the reference doc for CFBundleIcons.CFBundlePrimaryIcon. My info.plist now includes this, following the mentioned docs: However, now I get a type missmatch error when validating — however the types are as described in the docs: What am I missing? Why even is this plist entry required now? Or is this a Bug? Help please

I'm getting the following error when attempting to create a leaderboard via the documented POST url. Here is the full error response: { "errors" : [ { "id" : "xxxxxx", "status" : "400", "code" : "ENTITY_INVALID", "title" : "The request entity is not valid json", "detail" : "The request entity data could not be processed. Please ensure you are sending valid json.", "meta" : { "position" : { "row" : 1, "column" : 1 } } } ] } Except what I'm sending IS valid JSON, emitted directly from JsonUtility and verified via JSONLint: {"data":{"type":"gameCenterLeaderboards","attributes":{"defaultFormatter":"INTEGER","referenceName":"TEST_AUTO","vendorIdentifier":"TEST_AUTO","submissionType":"MOST_RECENT_SCORE","sortScoreType":"DESC","scoreRangeStart":"0","scoreRangeEnd":"20000","recurrenceStartDate":"2025-06-25T13:00:00Z","recurrenceDuration":"PT30M","recurrenceRule":"FREQ=HOURLY;INTERVAL=1"},"relationships":{"gameCenterDetail":{"data":{"type":"gameCenterDetails","id":"xxxxxx"}}}}} This follows EXACTLY the pattern in the App Store Connect documentation. I've even tried sending the example JSON they give (swapping out the id and fixing the quotation marks) and the server rejects THAT as not being valid JSON. What am I doing wrong? Thanks!

Hi everyone, We’ve enabled both StoreKit External Purchase and StoreKit External Purchase Link entitlements for our app (“RoadRecord útnyilvántartó”) and confirmed they are active in Xcode and App ID configuration. However, the App Store Connect interface still does not display the section to configure the External Purchase Link (nor the “Alternative Payment” section), which blocks us from submitting the app. When trying to submit the app, we see this error: “To submit this app version, you must first set up your account for alternative payment.” There’s no UI to complete this step in App Store Connect. Case ID: 14557560 App ID: 1441553506 We’ve contacted Developer Technical Support and were advised to post here for escalation and further technical investigation. Any help or confirmation from Apple staff would be greatly appreciated. We are ready to submit as soon as the UI becomes available. Thanks! Gábor

Hi everyone, I'm encountering a persistent issue with App Store Connect and hoping someone has seen this before or can advise. I have an approved in-app purchase (product ID: inspo_credits_10), and everything is correctly configured: The IAP is Approved and Ready for Sale The capability is enabled in both the Apple Developer portal and Xcode My app uses StoreKit correctly (Product.products(for:)) I’ve uploaded multiple builds (latest: version 1.3.8, build 3) The problem: When preparing the version (1.3.8) in App Store Connect, the “In-App Purchases” section does not appear at all — so I can’t attach the IAP to the version or submit it for review. I've tried: Re-uploading builds Creating new versions (1.3.9, 1.4.0…) Re-enabling the IAP capability Confirming that StoreKit is properly integrated Waiting multiple days for propagation Even creating new IAPs Still, the IAP section doesn’t appear when editing the version. Apple support responded, but directed me to Developer Technical Support without offering a fix or escalation path. Has anyone experienced this before — an approved IAP that doesn't show up in App Store Connect’s version editor? Is there a way to force a refresh or escalate this internally? Would appreciate any advice or direction!

Hi there, Recently, a change was made to the App Store Connect API, which removed the unofficially supported templateName parameter when creating provisioning profiles. This broke fastlane as it was using the templateName parameter. Could that change be reverted or official support added for templateName? I believe this change was first rolled out around March 18th and then reverted shortly after, before being rolled out again around May 6th. The fastlane issue can be seen here: https://github.com/fastlane/fastlane/issues/29498 Official AppStoreConnect API docs for the endpoint are here: https://developer.apple.com/documentation/appstoreconnectapi/profilecreaterequest/data-data.dictionary/attributes-data.dictionary

I just started with App Clips so quite new to it. One of our dependencies is very big in size (85+ MB) which is making the app size almost 87MB's uncompressed and 40MB's compressed with just this dependency and no other app clip related code in it. I created a App Thinning size report for the app clip and even with bigger app clip size, I decided to upload the beta build to App Store Connect for testing purposes. On App Store Connect, app clip size is 70+ MB and to my surprise it passed the App Store Connect review and I was able to install this app clip on my device from Test Flight. If I add functionality to the app clip with this bigger dependency SDK, then the app clip size is going to increase further and am worried that it could get rejected when I push it to app store. Minimum iOS version of the app is 16.4, so my understanding is that the maximum app clip size allowed is 15MB. Am trying to figure out, how the app clip build was approved on app store connect and if dependency sizes in app clips are ignored? Attaching screenshot of App Thinning report and screenshot of App Store Connect build with this App Clip.

Hi, I'm working on an app that currently support iOS 16+ I'm considering to raise the deployment target to iOS 26 For users on devices with version lower than iOS 26, I know they can continue to use the app they have already installed and can even redownload it via the last-compatible versions support. The question is simple - once the version with deployment target iOS 26 is released, is there any way to update the last compatible version of iOS 16+ in case a critical bug or security vulnerability has to be fixed? For example lets say that the current version is 1.2.2 (iOS 16+) new version 2.0.0 (iOS 26+) is released users with iOS 26 can install 2.0.0 existing users with iOS 16-18 can continue to use and reinstall 1.2.2 in the meanwhile, the app evolves and reaches 2.1.5 6 moths later, a critical bug or security vulnerability on 1.2.2 has to be fixed, so 1.2.3 version, based on 1.2.2 codebase with the necessary fixes has to be deployed to old users. How to update existing users with iOS 16-18 from 1.2.2 to 1.2.3? Is there any mechanism to achieve this? Does AppStoreConnect or AppStoreConnectAPI allow such thing?

Hello, I've noticed the prices of my products in my Xcode synced StoreKit configuration are not updated when I change the price in App Store Connect. I tried to manually sync the file, to remove and add it again to my project but old initial prices are still used. In the screenshot below, the price is currently $2.99 but the file still uses the initial price of $1.99. It makes testing a little bit painful because I'm never sure which product is being shown. Is this a bug? Is there a way to get the live production App Store prices be used instead of the starting prices? I filed a feedback for this: FB17798486 Regards, Axel

Hi, My developer payment was marked as "Paid" on June 5, 2025 in App Store Connect. As of June 16, the funds have still not arrived in my bank account. Apple only provides a Transaction ID (324756355), but no EFT or SWIFT reference number. My bank confirmed there is no record of any incoming or returned payment. Other developers have received their June 5 payments already. Mine seems to be either not sent or stuck. Apple support keeps telling me to wait 30 days, but without proof of actual transfer, this isn’t acceptable. Has anyone experienced this kind of delay before? Thanks.

Apple just introduced a new Challenges feature in Game Center (WWDC 2025). I have Game Center enabled for my app and have working leaderboards (and achievements). Now I want to implement challenges (connected to my leaderboards). But the Game Center Challenges not showing in App Store Connect or Xcode 16.4 I have a working GameCenterResources file in Xcode and it allows me to add Achievement, Leaderboard, Leaderboard Set, but no Challenges. I'm based out of Europe. Any ideas?

I inadvertently used the build number for the version number. How can I remove these versions/builds so that i can get back to my normal versioning scheme? I am now stuck using a version number of 110 instead of a build number of 110.

My app / subscription gets rejected with the following: Guideline 2.1 - Performance - App Completeness We have returned your in-app purchase products to you as the required binary was not submitted. When you are ready to submit the binary, please resubmit the in-app purchase products with the binary. and Your first subscription must be submitted with a new app version. Create your subscription, then select it from the app’s In-App Purchases and Subscriptions section on the version page before submitting the version to App Review. Once your binary has been uploaded and your first subscription has been submitted for review, additional subscriptions can be submitted from the Subscriptions section. Learn More ...ive tried all kinds. I archive a new build, upload it, update the app information top show new build so it ties in...and still nothing works. it is incredible frustrating. Can anyone help please. Ive wasted days on this

Hi, I'm integrating in-app subscriptions using StoreKit 2 in my iOS app, and I've run into an issue where I'm unable to fetch any subscription products via: let products = try await Product.products(for: productIDs) This consistently returns an empty result (products.count == 0) when running on a real device using a sandbox account. Here's some relevant context of my current setup: This is the first version of the app adding in-app purchase subscriptions. In-App Purchase products are configured in App Store Connect, and marked as "Ready to Submit". The products are attached to the app version, and fully saved. A sandbox account is logged in on the test device. StoreKit Configuration local debug works fine — I can simulate purchases locally from Xcode. However, in the real sandbox environment, any attempt to fetch products returns no results. In App Store Connect > Agreements, Tax, and Banking, I currently see: Paid Application Agreement: Status = "Waiting for User Info" Banking Info: “In Progress” Tax Info: Not yet submitted ❓❓❓ My key question is: Does the "Paid Applications Agreement" need to be fully active (including bank + tax info complete) before in-app purchase products can be fetched in the sandbox environment? If so, it seems that this may be blocking my ability to: Test real subscription flows with sandbox accounts Pass App Store Review (since products cannot be loaded) Any clarification would be greatly appreciated! Thanks in advance.

Dear Experts, What is the current best practice for build numbering? I ask because I am aware that when exporting an archived app for upload I am now asked if I want Xcode to manage the build number for me. In the past I have set a build number in the Info.plist, often based on the date, e.g. 2.4.20230218. Now, I am asked if I want that to be replaced by something like 2.4.7 (if I recall correctly). So far I've answered No. Previously I have searched for automatic build numbering and I've found web pages that suggest adding a script to the build process that automatically increments the build number in the info.plist, or similar. I've not tried to implement that myself. In some of my apps, I have code that needs to know the full version at compile time (e.g. app receipt validation). How would that interact with the new feature? Thanks, Phil.

I am having issues deploying my iOS app, that uses ShazamKit, to get working on a Mac with Apple silicon. When uploading the archive to App Store Connect I do get ITMS-90863: Macs with Apple silicon support issue - The app links with libraries that aren’t present in macOS: /usr/lib/swift/libswiftShazamKit.dylib Is ShazamKit not supported for iOS apps that can run on Macs with Apple silicon? Or is there something I should fix in my setup / deployment?

Hi Apple Developer Support, We're currently implementing auto-renewable subscriptions in a React Native app using the react-native-iap library. The subscription purchases are working as expected in Sandbox. We receive the transaction and purchaseUpdatedListener gives us a valid-looking transactionReceipt However, when we attempt to validate this receipt with Apple's servers, the response consistently returns status code 21002, indicating that the receipt data is either malformed or missing. We’ve confirmed the receipt is well-formed, properly passed as received, and well above the minimum size expected. The shared secret is correctly configured and matches the subscription group. We're using the correct sandbox endpoint and ensuring no modification is done to the receipt before validation. Despite this, validation fails every time. We are looking for guidance or clarification on what might cause this status, especially when the receipt is coming directly from the system after a successful test purchase. const purchaseUpdateSub = purchaseUpdatedListener(async (purchase) => { console.log("🛒 Purchase Updated:", purchase); const receipt = purchase.transactionReceipt; if (!receipt) { Alert.alert("Error", "No receipt found."); setLoading(false); return; } }); the response is: { "status": 21002 } Any guidance on why this might be happening would be appreciated. Thanks!

Hello everyone The in-app subscription / purchase aren't loading in the version of my app that I'm submitting onto App Store Connect. Locally, I use StoreKit config to test/develop my app. I already have my subscription groups and legal stuff set up properly. However, when I goto my subscription group, a blue notice says Your first subscription must be submitted with a new app version. Create your subscription, then select it from the app’s In-App Purchases and Subscriptions section on the version page before submitting the version to App Review. Once your binary has been uploaded and your first subscription has been submitted for review, additional subscriptions can be submitted from the Subscriptions section. Learn More But when I goto Appstore Connect -> Apps -> the app I'm working on -> iOS -> Version 1.0 Prepare for Submission, I can't find any section regarding "In-App Purchases and Subscriptions". I also can't find it after going into the build by clicking on the build number(there's only Test Information and Build Metadata)

We are trying to implement / test in-app purchase for our subscription purchase in the app. We have done all the steps listed in the documentation on apple's website; and Our subscription plan is sitting in 'Ready to Submit' state. However, we are getting an empty response from, final response = await _iap.queryProductDetails({'com.company.xyz.basic1m'}); debugPrint(" Check: ${response.toString()}"); debugPrint("❌ Responses: ${response.productDetails.map((ProductDetailsResponse)=>ProductDetailsResponse.toString()).toList()}"); debugPrint("❌ Responses: ${response.productDetails.length}"); if (response.notFoundIDs.isNotEmpty) { debugPrint("❌ Not found: ${response.notFoundIDs}"); } else if (response.productDetails.isNotEmpty) { debugPrint("✅ Product loaded: ${response.productDetails.first.title}"); } The response we get is, flutter: Check: Instance of 'ProductDetailsResponse' flutter: ❌ Responses: [] flutter: ❌ Responses: 0 flutter: ❌ Not found: [com.company.xyz.basic1m] Note: We are testing with a real device iphone 13 mini via Xcode. We tried to test using, ''com.apple.test.Subscription1.monthly'', as instructed but we have not been successful with that. And seems like (based on online search), it doesn't work all the time. We also searched online for a solution, and some of the forums suggest that we have to submit the app for review when adding subscription for the first time. It doesn't mention the same that in the apple documentation. It confusing. Help and guidance in this regard would be really appreciated.

Is it only me (or a localisation issue in french) or is there a bug in the submission form (buttons titles): But acceptance (dark blue button) works as intended.

Hello, I submitted my mobile game to the App Store with in-app purchase items. I initially sent my in-app purchases for review for the first time. I had fixed a bug before and thought I could submit a new build with the fix. (Before too much time has passed)I withdrew the previous build and re-submitted the new one. Now, I cannot select in-app purchase items in the new build, and the in-app purchases are still in “Waiting for Review.” Did they get stuck? It has been one day. Even if the in-app purchases get approved, I am unable to choose them in the new build.